Multi-Computer Tool for Tracking and Analysis of BOT Performance

ABSTRACT

Aspects of the disclosure relate to intelligent bot performance tracking and analysis. A computing platform may receive a work queue of items to be processed using a bot. The computing platform may receive, in real-time with processing of the work queue using the bot, metadata associated with the work queue. Based on the metadata, the computing platform may assign, in real-time, a value metric associated with completion of each item in the work queue. Based on the assigned value metric, the computing platform may identify a robotic process automation cost associated with processing the work queue via the bot. The computing platform may compare, the robotic process automation cost to a cost to process the work queue via another operation, and determine a performance metric for the bot based on the comparison. The computing platform may dynamically generate and transmit, in real-time, an indication of the determined bot performance metric.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to co-pendingU.S. application Ser. No. 17/510,971, filed Oct. 26, 2021, and entitled,“Multi-Computer Tool for Tracking and Analysis of Bot Performance,”which is incorporated herein by reference in its entirety.

BACKGROUND

Aspects of the disclosure generally relate to one or more computersystems, servers, and/or other devices including hardware and/orsoftware. In particular, one or more aspects of the disclosure relate toan intelligent bot tool for tracking and facilitating analysis of botperformance.

Robotic process automation (RPA) may offer a number of benefits, such asreducing manual and repetitive tasks, which leads to cost reduction andtime savings, for example. In many instances, it may be difficult toquantify those benefits. In some instances, bot performance may becaptured manually through the use of spreadsheets. In many instances, itmay be difficult to accurately and consistently track bot performancethat results from automating a process.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects of the disclosure. The summary is not anextensive overview of the disclosure. It is neither intended to identifykey or critical elements of the disclosure nor to delineate the scope ofthe disclosure. The following summary merely presents some concepts ofthe disclosure in a simplified form as a prelude to the descriptionbelow.

Aspects of the disclosure provide effective, efficient, scalable, andconvenient technical solutions that address and overcome the technicalproblems associated with evaluating the effectiveness of robotic processautomation. In accordance with one or more embodiments, a computingplatform having at least one processor, a communication interface, andmemory may receive a work queue of items to be processed using a roboticprocess automation (RPA) bot. Subsequently, the computing platform mayreceive, in real-time with processing of the work queue of items usingthe bot, metadata associated with the work queue of items. Next, thecomputing platform may assign, in real-time, based on the metadata, avalue metric associated with completion of each item in the work queueof items. Thereafter, the computing platform may identify, based on theassigned value metric, a robotic process automation cost associated withprocessing the work queue of items via the bot. The computing platformmay compare the robotic process automation cost to a cost to process thework queue of items via another operation. The computing platform maydetermine a performance metric for the bot based on the comparison.Then, the computing platform may dynamically generate, in real-time, anindication of the determined performance metric for the bot. Thecomputing platform may transmit, to a user computing device for display,the dynamically generated indication.

In some embodiments, the computing platform may, based on theperformance metric for the bot being below a predetermined threshold,halt processing of the work queue of items using the bot.

In some arrangements, assigning the value metric associated withcompletion of each item in the work queue of items may includeretrieving one or more value metrics from a database.

In some examples, the value metric may include a value in a currency.

In some embodiments, the computing platform may dynamically update theperformance metric for the bot as new items in the work queue of itemsare processed.

In some example arrangements, the bot may be an attended bot. In someembodiments, the bot may be an unattended bot.

In some examples, the cost to process the work queue of items viaanother operation may be associated with implementing functions of thebot via a method other than robotic process automation.

In some embodiments, identifying the robotic process automation cost mayinclude identification of one or more of: a salary cost, a build cost, alicense cost, or a support cost.

In some embodiments, each item in the work queue of items may correspondto a transaction processing task.

These features, along with many others, are discussed in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIGS. 1A and 1B depict an illustrative computing environment forintelligent bot performance tracking and analysis in accordance with oneor more example arrangements;

FIGS. 2A-2D depict an illustrative event sequence for intelligent botperformance tracking and analysis in accordance with one or more examplearrangements;

FIG. 3 depicts an example graphical user interface for intelligent botperformance tracking and analysis in accordance with one or more examplearrangements; and

FIG. 4 depicts an illustrative method for intelligent bot performancetracking and analysis in accordance with one or more examplearrangements.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized, and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

It is noted that various connections between elements are discussed inthe following description. It is noted that these connections aregeneral and, unless specified otherwise, may be direct or indirect,wired or wireless, and that the specification is not intended to belimiting in this respect.

As a brief introduction to the concepts described further herein, one ormore aspects of the disclosure relate to evaluating the effectiveness ofrobotic process automation. In particular, one or more aspects of thedisclosure allow a system to uniformly measure the performance, such asa return on investment (ROI) of an RPA deployment in real-time. In someembodiments, the performance or performance measure may include an ROIthat may be a cumulative savings amount that is calculated as bots arerun. For instance, as a bot is run, a number of widgets or transactionsproduced by the bot may be tracked and a benefit may be quantified inreal-time. Additional aspects of the disclosure may provide a proof ofconcept that a bot runs optimally (e.g., that it increased efficiencyand achieved the expected financial objectives). Further aspects of thedisclosure may identify an organization's automation potential.

FIGS. 1A and 1B depict an illustrative computing environment forintelligent bot performance tracking and analysis in accordance with oneor more example arrangements. Referring to FIG. 1A, computingenvironment 100 may include one or more devices (e.g., computer systems,communication devices, servers). For example, computing environment 100may include a bot performance evaluation computing platform 110, anenterprise server infrastructure 120, an enterprise user computingdevice 130, and a bot host server 140.

As described further below, bot performance computing platform 110 maybe a computer system that includes one or more computing devices (e.g.,servers, server blades, or the like) and/or other computer components(e.g., processors, memories, communication interfaces) that may be usedto implement bot performance tracking and analysis, or the like to trackbot performance and monitor bots in real-time to determine botperformance accordingly. In some instances, bot performance computingplatform 110 may be maintained by an enterprise organization (e.g., afinancial institution, or the like) and may be configured to receiveprocess step information relating to one or more enterprise processesand determine a performance measure, such as ROI, of a bot in completinga current work queue. In some instances, bot performance computingplatform 110 may be configured to maintain a robotic process automationmodel that stores correlations between process step information, andother parameters relating to completing a workload, and may beconfigured to update the bot performance based on received information.

Enterprise server infrastructure 120 may include one or more computingdevices and/or other computer components (e.g., processors, memories,communication interfaces). In some arrangements, enterprise serverinfrastructure 120 may include a server, server blade, or the likeconfigured to host an enterprise service (e.g., a mobile bankingapplication, ATM service, or the like). In one or more instances, theenterprise server infrastructure 120 may be configured to communicatewith enterprise user devices (e.g., enterprise user computing device130, or the like) to process workload based on various parameters anduser inputs received at enterprise user devices. In some instances, theenterprise server infrastructure 120 may be configured to cause display(e.g., at enterprise user computing device 130, or the like), of aparticular user interface based on information received from botperformance computing platform 110.

Enterprise user device 130 may include one or more computing devicesand/or other computer components (e.g., processors, memories,communication interfaces). In some arrangements, enterprise usercomputing device 130 may be a desktop computer, laptop computer, tablet,mobile device, or the like, and may be used by an individual such as aclient or employee of an enterprise organization (e.g., a financialinstitution, or the like). For example, enterprise user computing device130 may be configured to communicate with enterprise serverinfrastructure 120 to facilitate display of user interfaces (e.g.,interfaces that generate a report of a performance measure, such as ROI,associated with a bot, updates to the performance calculations, or thelike) based on received workload information.

In some arrangements, enterprise user computing device 130 may be linkedto and/or used by one or more enterprise users (who may, e.g., beemployees of an enterprise organization operating the enterprise centerwhere enterprise user computing device 130 is deployed and/or used). Forinstance, enterprise user computing device 130 may be deployed at anenterprise center, such as the enterprise center where enterprise serverinfrastructure 120 is deployed, so that enterprise user computing device130 may be used by one or more employees of an enterprise organizationoperating the enterprise center. For example, enterprise user computingdevice 130 may store and/or execute one or more enterprise applications,such as account creation and management applications, transactionhistory applications, lending applications, brokerage applications,and/or other applications, which may be used by the one or moreenterprise users of enterprise user computing device 130.

Bot host server 140 may include one or more computing devices and/orother computer components (e.g., processors, memories, communicationinterfaces). In addition, bot host server 140 may include a botorchestrator which may be configured to generate, host, transmit, and/orotherwise provide one or more bots (which may, e.g., process items froma work queue using at least one bot). The bots may be software agentsprovisioned by robotic process automation using user interface (UI) andsurface-level features to create scripts that automate tasks (e.g.,routine, predictable tasks). In some examples, the bots may beprovisioned after a review and approval process.

Computing environment 100 also may include one or more networks, whichmay interconnect bot performance computing platform 110, enterpriseserver infrastructure 120, enterprise user computing device 130, bothost server 140, or the like. For example, computing environment 100 mayinclude a network 150 (which may interconnect, e.g., bot performancecomputing platform 110, enterprise server infrastructure 120, enterpriseuser computing device 130, bot host server 140, and/or one or more othersystems which may be associated with an enterprise organization, such asa financial institution, with one or more other systems, publicnetworks, sub-networks, and/or the like).

In one or more arrangements, bot performance computing platform 110,enterprise server infrastructure 120, enterprise user computing device130, and bot host server 140, may be any type of computing devicecapable of sending and/or receiving workload data and processing theworkloads accordingly. For example, bot performance computing platform110, enterprise server infrastructure 120, enterprise user computingdevice 130, bot host server 140, and/or the other systems included incomputing environment 100 may, in some instances, be and/or includeserver computers, desktop computers, laptop computers, tablet computers,smart phones, or the like that may include one or more processors,memories, communication interfaces, storage devices, and/or othercomponents. As noted above, and as illustrated in greater detail below,any and/or all of bot performance computing platform 110, enterpriseserver infrastructure 120, enterprise user computing device 130, and/orbot host server 140 may, in some instances, be special-purpose computingdevices configured to perform specific functions as described herein.

As illustrated in greater detail below, bot performance computingplatform 110 may include one or more computing devices configured toperform one or more of the functions described herein. For example, botperformance computing platform 110 may include one or more computers(e.g., laptop computers, desktop computers, servers, server blades, orthe like).

Referring to FIG. 1B, bot performance computing platform 110 may includeone or more processors 111, memory 112, and communication interface 113.A data bus may interconnect processor 111, memory 112, and communicationinterface 113. Communication interface 113 may be a network interfaceconfigured to support communication between bot performance computingplatform 110 and one or more networks (e.g., network 150, or the like).Memory 112 may include one or more program modules having instructionsthat when executed by processor 111 cause bot performance computingplatform 110 to perform one or more functions described herein and/orone or more databases that may store and/or otherwise maintaininformation which may be used by such program modules and/or processor111. In some instances, the one or more program modules and/or databasesmay be stored by and/or maintained in different memory units of botperformance computing platform 110 and/or by different computing devicesthat may form and/or otherwise make up bot performance computingplatform 110. For example, memory 112 may have, host, store, and/orinclude bot performance module 112 a, robotic process automationdatabase 112 b, and value identification module 112 c.

Bot performance module 112 a may have instructions that direct and/orcause bot performance module 112 a to execute robotic process automationtracking techniques related to RPA-based workloads, as discussed ingreater detail below. Bot performance database 112 b may storeinformation used by bot performance module 112 a and/or bot performancecomputing platform 110 in application of robotic process automationtracking techniques related to completing RPA-based workloads (e.g.,using metadata to capture an ROI), and/or in performing other relatedfunctions for processing and maintaining enterprise-managed informationand resources. Value identification module 112 c may have instructionsthat direct and/or cause bot performance computing platform 110 to set,define, and/or iteratively refine values (e.g., associated with at leastone transaction or unit of work) used by bot performance computingplatform 110 and/or other systems in computing environment 100.

FIGS. 2A-2D depict an illustrative event sequence for intelligent botperformance tracking and analysis in accordance with one or more examplearrangements. Referring to FIG. 2A, at step 201, bot performancecomputing platform 110 may establish a connection with enterprise serverinfrastructure 120. For example, bot performance computing platform 110may establish a first wireless data connection with enterprise serverinfrastructure 120 to link bot performance computing platform 110 withenterprise server infrastructure 120. In some instances, bot performancecomputing platform 110 may identify whether or not a connection isalready established with the enterprise server infrastructure 120. If aconnection is already established with enterprise server infrastructure120, bot performance computing platform 110 might not re-establish theconnection. If a connection is not yet established with enterpriseserver infrastructure 120, bot performance computing platform 110 mayestablish the first wireless data connection as described above.

At step 202, bot performance computing platform 110 may establish aconnection with enterprise user computing device 130. For example, botperformance computing platform 110 may establish a second wireless dataconnection with enterprise user computing device 130 to link botperformance computing platform 110 with enterprise user computing device130. In some instances, bot performance computing platform 110 mayidentify whether or not a connection is already established withenterprise user computing device 130. If a connection is alreadyestablished with enterprise user computing device 130, bot performancecomputing platform 110 might not re-establish the connection. If aconnection is not yet established with the enterprise user computingdevice 130, bot performance computing platform 110 may establish thesecond wireless data connection as described above.

At step 203, bot performance computing platform 110 may receive processstep information (e.g., a work queue of items) associated with a givenbot. Each item in the work queue of items may correspond to atransaction processing task. For example, transaction processing tasksmay include actions such as collecting data, filtering out information,transferring data to a destination, and may be associated with work suchas invoice processing, loan processing, document transfer, otherenterprise-related process tasks, etc.). In some examples, the processstep information may be sent from the enterprise server infrastructureand/or the enterprise user computing device 130. The process stepinformation may be sent or loaded by a process running on a server inthe enterprise server infrastructure 120. In some examples, botperformance computing platform 110 may receive the process stepinformation from one or more data source computer systems (e.g., fromenterprise server infrastructure 120, enterprise user computing device130, and/or one or more other data sources). The process stepinformation may, for instance, include data that is transmitted byand/or received from internal event feeds (e.g., feeds originating fromsources within the enterprise organization), external event feeds (e.g.,feeds originating from sources outside of the enterprise organization),internal enterprise systems (e.g., systems within the enterpriseorganization), external enterprise systems (e.g., systems outside of theenterprise organization), and/or other sources.

For example, at step 203, bot performance computing platform 110 mayreceive, via the communication interface (e.g., communication interface113) and while the first and/or second wireless data connection isestablished, from one or more data source computer systems (e.g., fromenterprise server infrastructure 120, enterprise user computing device130, and/or one or more other data sources), a work queue of items to beprocessed using a robotic process automation (RPA) bot. In someexamples, the bot may be an attended bot (e.g., triggered by userevents). In some examples, the bot may be an unattended bot (e.g.,automated end-to-end).

At step 204, bot performance computing platform 110 may establish aconnection with bot host server 140. For example, bot performancecomputing platform 110 may establish a third wireless data connectionwith bot host server 140 to link bot performance computing platform 110with bot host server 140. In some instances, bot performance computingplatform 110 may identify whether or not a connection is alreadyestablished with the bot host server 140. If a connection is alreadyestablished with bot host server 140, bot performance computing platform110 might not re-establish the connection. If a connection is not yetestablished with bot host server 140, bot performance computing platform110 may establish the third wireless data connection as described above.

Referring to FIG. 2B, at step 205, bot host server 140 may determineavailability of one or more bots, assign tasks to one or more bots(e.g., based on availability and capability), schedule one or more botsto run (e.g., based on prioritization of work queues), and process andcomplete the work queue using the one or more bots. In some instances,step 205 may include transmitting a notification to the bot performancecomputing platform 110 that the work queue has been completed. At step206, the bot host server 140 may generate and send metadata informationrelating to the processing and completion of the work queue to the botperformance computing platform 110, the enterprise server infrastructure120 and/or the enterprise user computing device 130. For instance, atstep 206, metadata information related to the work queue may be added toa database on the enterprise server infrastructure 120, enterprise usercomputing device 130, bot performance computing platform 110, and/or thelike.

At step 207, bot performance computing platform 110 may receive, inreal-time with processing of the work queue of items using the bot, themetadata information associated with the work queue of items. Forexample, the metadata information may be sent from the enterprise serverinfrastructure 120 and/or the enterprise user computing device 130. Themetadata information may be sent or loaded by a process running on aserver in the enterprise server infrastructure 120.

For example, at step 207, bot performance computing platform 110 mayreceive, via the communication interface (e.g., communication interface113) and while the first and/or second wireless data connection isestablished, from one or more data source computer systems (e.g., fromenterprise server infrastructure 120, enterprise user computing device130, and/or one or more other data sources), metadata information. Themetadata information may, for instance, include transaction metadata.The metadata information may, for instance, identify information aboutspecific transactions being conducted (e.g. automatically by a computersystem or manually by an individual) as part of a given process. Forexample, the metadata may be indicative of a measure associated with atransaction processing task (e.g., a time to complete an item in thework queue, resources used to complete an item in the work queue, etc.).

At step 208, based on the received metadata information, bot performancecomputing platform 110 may assign (e.g., via value identification module112 c), in real-time, a value metric associated with completion of eachitem in the work queue of items. For example, bot performance computingplatform 110 may assign a value (e.g., a benefit or cost savings) toeach item in the work queue of items corresponding to a transactionprocessing task. The value metric associated with completion of eachitem in the work queue of items may be assigned based on industrystandards or guidelines, standards as established by an enterprise, orthe like. In some examples, in assigning the value metric associatedwith completion of each item in the work queue of items, bot performancecomputing platform 110 may retrieve the one or more value metrics from adatabase (e.g., a database on the enterprise server infrastructure 120,enterprise user computing device, bot performance computing platform110, or the like). In some instances, the value metric may include avalue in a currency (e.g., in dollars or other currency or standard ofvalue).

Referring to FIG. 2C, at step 209, bot performance computing platform110 may identify, based on the assigned value metric, a robotic processautomation cost associated with processing the work queue of items viathe bot. In some examples, the identified robotic process automationcost may include a salary cost (e.g., salaries of developers or botbuilders), a build cost (e.g., to design, build, test, and deploy thebot), a license cost (e.g., software licenses), a support cost (e.g.,governance costs, patching, releases), and/or the like.

At step 210, bot performance computing platform 110 may identify a costto process the work queue of items via another operation (e.g., via amanual operation or a method other than robotic process automation). Forexample, the cost of an existing manual process may include a number offull-time equivalent (FTE) individuals, a cost of the FTE individuals(e.g., annual total FTE wages), a number of times a process is performed(e.g., per day), an amount of time required to perform a process (e.g.,in minutes or hours), and/or the like.

At step 211, bot performance computing platform 110 may compare therobotic process automation cost to the cost to otherwise perform thefunctions of the bot (e.g., implementing functions of the bot manuallyor via a method other than robotic process automation).

At step 212, bot performance computing platform 110 may determine aperformance metric, such as return on investment (ROI) for the bot basedon the comparison. In determining the performance metric, botperformance computing platform 110 may, for instance, identify how muchvalue is saved or could be saved by eliminating or optimizing one ormore process steps using an RPA bot.

Referring to FIG. 2D, in some examples, at step 213, a predeterminedthreshold (e.g., ROI threshold value) may be set, and the performancemetric (e.g., ROI) compared to the predetermined threshold. Thepredetermined threshold may be established by an enterpriseorganization, for example. Based on the performance metric (e.g., ROI)for the bot being below the predetermined threshold (e.g., an ROI fallsshort of assumptions), bot performance computing platform 110 may, atstep 213, halt processing of the work queue of items using the bot. Forinstance, if a bot's performance is determined to be suboptimal, the botmay be further optimized or disabled for further maintenance anddevelopment. Otherwise, the processing of the work queue of items usingthe bot will continue.

At step 214, bot performance computing platform 110 may dynamicallygenerate, in real-time, an indication of the determined performancemetric for the bot. In some examples, bot performance computing platform110 may dynamically update the performance metric for the bot as newitems in the work queue of items are processed. Accordingly, in someexamples, evaluation of bot performance may be continuously performed,thereby providing a real-time indication of bot performance.

At step 215, bot performance computing platform 110 may transmit, viathe communication interface (e.g., communication interface 113) andwhile the second wireless data connection is established, to a usercomputing device (e.g., enterprise user computing device 130) fordisplay, the dynamically generated indication. In turn, at step 216, theuser computing device (e.g., enterprise user computing device 130) maydisplay the real-time performance metrics. In providing the displayrelated to the performance metric (e.g., ROI) of the bot processing theassociated work queue of items, bot performance computing platform 110may generate and/or send information to a device linked to an enterpriseassociate (e.g., enterprise user computing device 130) which may causeenterprise user computing device 130 to generate, display, and/orotherwise present a graphical user interface similar to graphical userinterface 300, which is illustrated in FIG. 3 . As seen in FIG. 3 ,graphical user interface 300 may include text and/or other informationindicating that a current work queue has been completed and providing anindication of efficiency increases provided as a result of using botperformance computing platform 110 (e.g., “The current work queue hasbeen completed. Using Bot A increased the efficiency of completing thework queue by [##]%.”), providing the workload completion resultsproduced using the bot (e.g., timing to complete the work queue,resources used to complete the work queue, savings per year, and thelike), as well as one or more user-selectable controls allowing the userof enterprise user computing device 130 to view the additional datarelating to bot performance and associated parameters (e.g., “ViewAdditional Data”). In this way, a user may view the benefits of an RPAsolution in real-time.

Subsequently, bot performance computing platform 110 may repeat one ormore steps of the example event sequence discussed above in tracking andfacilitating analysis of bot performance. Additionally or alternatively,bot performance computing platform 110 may initiate one or more workloadanalysis processes and/or generate and send one or more data resultsinterfaces, similar to how bot performance computing platform 110 mayinitiate such processes and generate and send such interfaces in theexamples described above.

FIG. 4 depicts an illustrative method for intelligent bot performancetracking and analysis in accordance with one or more exampleembodiments. Referring to FIG. 4 , at step 405, a computing platformhaving at least one processor, a communication interface, and memorymay, receive a work queue of items to be processed using a roboticprocess automation (RPA) bot. At step 410, the computing platform mayreceive, in real-time with processing of the work queue of items usingthe bot, metadata associated with the work queue of items. At step 415,the computing platform may assign, in real-time, based on the metadata,a value metric associated with completion of each item in the work queueof items. At step 420, the computing platform may identify, based on theassigned value metric, a robotic process automation cost associated withprocessing the work queue of items via the bot. At step 425, thecomputing platform may compare the robotic process automation cost to acost to process the work queue of items via another operation. At step430, the computing platform may determine a performance metric for thebot based on the comparison. At step 435, the computing platform maydynamically generate, in real-time, an indication of the determinedperformance metric for the bot, and transmit the dynamically generatedindication to a user computing device for display. At step 440, thecomputing platform may dynamically update the performance metric for thebot as new items in the work queue of items are processed.

One or more aspects of the disclosure may be embodied in computer-usabledata or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices to performthe operations described herein. Generally, program modules includeroutines, programs, objects, components, data structures, and the likethat perform particular tasks or implement particular abstract datatypes when executed by one or more processors in a computer or otherdata processing device. The computer-executable instructions may bestored as computer-readable instructions on a computer-readable mediumsuch as a hard disk, optical disk, removable storage media, solid-statememory, RAM, and the like. The functionality of the program modules maybe combined or distributed as desired in various embodiments. Inaddition, the functionality may be embodied in whole or in part infirmware or hardware equivalents, such as integrated circuits,application-specific integrated circuits (ASICs), field programmablegate arrays (FPGA), and the like. Particular data structures may be usedto more effectively implement one or more aspects of the disclosure, andsuch data structures are contemplated to be within the scope of computerexecutable instructions and computer-usable data described herein.

Various aspects described herein may be embodied as a method, anapparatus, or as one or more computer-readable media storingcomputer-executable instructions. Accordingly, those aspects may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, an entirely firmware embodiment, or an embodiment combiningsoftware, hardware, and firmware aspects in any combination. Inaddition, various signals representing data or events as describedherein may be transferred between a source and a destination in the formof light or electromagnetic waves traveling through signal-conductingmedia such as metal wires, optical fibers, or wireless transmissionmedia (e.g., air or space). In general, the one or morecomputer-readable media may be and/or include one or more non-transitorycomputer-readable media.

As described herein, the various methods and acts may be operativeacross one or more computing servers and one or more networks. Thefunctionality may be distributed in any manner, or may be located in asingle computing device (e.g., a server, a client computer, and thelike). For example, in alternative embodiments, one or more of thecomputing platforms discussed above may be combined into a singlecomputing platform, and the various functions of each computing platformmay be performed by the single computing platform. In such arrangements,any and/or all of the above-discussed communications between computingplatforms may correspond to data being accessed, moved, modified,updated, and/or otherwise used by the single computing platform.Additionally or alternatively, one or more of the computing platformsdiscussed above may be implemented in one or more virtual machines thatare provided by one or more physical computing devices. In sucharrangements, the various functions of each computing platform may beperformed by the one or more virtual machines, and any and/or all of theabove-discussed communications between computing platforms maycorrespond to data being accessed, moved, modified, updated, and/orotherwise used by the one or more virtual machines.

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one or more of the steps depicted in theillustrative figures may be performed in other than the recited order,and one or more depicted steps may be optional in accordance withaspects of the disclosure.

What is claimed is:
 1. A computing platform, comprising: at least oneprocessor; a communication interface communicatively coupled to the atleast one processor; and memory storing computer-readable instructionsthat, when executed by the at least one processor, cause the computingplatform to: receive a work queue of items to be processed using arobotic process automation (RPA) bot; receive, in real-time withprocessing of the work queue of items using the bot, metadata associatedwith the work queue of items; assign, in real-time, based on themetadata, a value metric associated with completion of each item in thework queue of items; identify, based on the assigned value metric, arobotic process automation cost associated with processing the workqueue of items via the bot; compare, the robotic process automation costto a cost to process the work queue of items via another operation;determine a performance metric for the bot based on the comparison; andtransmit, to a user computing device for display, the performance metricfor the bot.
 2. The computing platform of claim 1, wherein the memoryfurther stores computer-readable instructions that, when executed by theat least one processor, cause the computing platform to: based on theperformance metric for the bot being below a predetermined threshold,halt processing of the work queue of items using the bot.
 3. Thecomputing platform of claim 1, wherein assigning the value metricassociated with completion of each item in the work queue of itemscomprises retrieving one or more value metrics from a database.
 4. Thecomputing platform of claim 1, wherein the value metric comprises avalue in a currency.
 5. The computing platform of claim 1, wherein thememory further stores computer-readable instructions that, when executedby the at least one processor, cause the computing platform to:dynamically update the performance metric for the bot as new items inthe work queue of items are processed.
 6. The computing platform ofclaim 1, wherein the bot is an attended bot.
 7. The computing platformof claim 1, wherein the bot is an unattended bot.
 8. The computingplatform of claim 1, wherein the cost to process the work queue of itemsvia another operation is associated with implementing functions of thebot via a method other than robotic process automation.
 9. The computingplatform of claim 1, wherein identifying the robotic process automationcost further comprises identifying one or more of: a salary cost, abuild cost, a license cost, or a support cost.
 10. The computingplatform of claim 1, wherein each item in the work queue of itemscorresponds to a transaction processing task.
 11. A method, comprising:at a computing platform comprising at least one processor, acommunication interface, and memory: receiving, by the at least oneprocessor, via the communication interface, a work queue of items to beprocessed using a robotic process automation (RPA) bot; receiving, bythe at least one processor, via the communication interface, inreal-time with processing of the work queue of items using the bot,metadata associated with the work queue of items; assigning, by the atleast one processor, in real-time, based on the metadata, a value metricassociated with completion of each item in the work queue of items;identifying, by the at least one processor, based on the assigned valuemetric, a robotic process automation cost associated with processing thework queue of items via the bot; comparing, by the at least oneprocessor, the robotic process automation cost to a cost to process thework queue of items via another operation; determining, by the at leastone processor, a performance metric for the bot based on the comparison;and transmitting, by the at least one processor, via the communicationinterface, to a user computing device for display, the performancemetric for the bot.
 12. The method of claim 11, further comprising:based on the performance metric for the bot being below a predeterminedthreshold, halting, by the at least one processor, processing of thework queue of items using the bot.
 13. The method of claim 11, whereinassigning the value metric associated with completion of each item inthe work queue of items comprises retrieving one or more value metricsfrom a database.
 14. The method of claim 11, wherein the value metriccomprises a value in a currency.
 15. The method of claim 11, furthercomprising: dynamically updating, by the at least one processor, theperformance metric for the bot as new items in the work queue of itemsare processed.
 16. The method of claim 11, wherein the bot is anunattended bot.
 17. The method of claim 11, wherein the cost to processthe work queue of items via another operation is associated withimplementing functions of the bot via a method other than roboticprocess automation.
 18. The method of claim 11, wherein identifying therobotic process automation cost further comprises identifying one ormore of: a salary cost, a build cost, a license cost, or a support cost.19. The method of claim 11, wherein each item in the work queue of itemscorresponds to a transaction processing task.
 20. One or morenon-transitory computer-readable media storing instructions that, whenexecuted by a computing platform comprising at least one processor, acommunication interface, and memory, cause the computing platform to:receive, via the communication interface, a work queue of items to beprocessed using a robotic process automation (RPA) bot; receive, via thecommunication interface, in real-time with processing of the work queueof items using the bot, metadata associated with the work queue ofitems; assign, in real-time, based on the metadata, a value metricassociated with completion of each item in the work queue of items;identify, based on the assigned value metric, a robotic processautomation cost associated with processing the work queue of items viathe bot; compare, the robotic process automation cost to a cost toprocess the work queue of items via another operation; determine aperformance metric for the bot based on the comparison; and transmit,via the communication interface, to a user computing device for display,the performance metric for the bot.